Skip to content

fix: use prefered name in FAP panels - #1266

Merged
TCMeldrum merged 4 commits into
developfrom
1496-update-panel-memebers-to-prefered-name
Dec 2, 2025
Merged

fix: use prefered name in FAP panels#1266
TCMeldrum merged 4 commits into
developfrom
1496-update-panel-memebers-to-prefered-name

Conversation

@TCMeldrum

@TCMeldrum TCMeldrum commented Nov 18, 2025

Copy link
Copy Markdown
Contributor

Closes: UserOfficeProject/issue-tracker#1496

Description

This PR introduces changes to use the preferred name of a user in FAP panels instead of the first name.

Motivation and Context

The change is required to enhance the user experience by addressing and referring to the users by their preferred name. It resolves the issue of misaddressing users who prefer to be known by names other than their first names.

Changes

  1. The 'Name' field in FapMembers.tsx, AssignFapMemberToProposalModal.tsx, FapAssignedReviewersTable.tsx, MultiRankAssignmentDialog.tsx, and PeopleTable.tsx has been updated to display the preferred name of the user if available, otherwise the first name.
  2. The 'preferredname' property of a user has been added to the selected items in PeopleTable.tsx to ensure the preferred name is available for display.

How Has This Been Tested?

Fixes Jira Issue

https://jira.esss.lu.se/browse/

Depends On

Tests included/Docs Updated?

  • I have added tests to cover my changes.
  • All relevant doc has been updated

>
<TableCell component="th" scope="row">
{row.firstname}
{row.preferredname ? row.preferredname : row.firstname}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering if we should always set the preferredname, so we do not need to do these checks everywhere. If a user has a preferredname we set it otherwise we set preferredame using name.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've open a issue to do a larger code wide change: UserOfficeProject/issue-tracker#1499

@TCMeldrum
TCMeldrum marked this pull request as ready for review November 21, 2025 10:46
@TCMeldrum
TCMeldrum requested a review from a team as a code owner November 21, 2025 10:46
@TCMeldrum
TCMeldrum requested review from ACLay and removed request for a team November 21, 2025 10:46
@github-actions
github-actions Bot force-pushed the 1496-update-panel-memebers-to-prefered-name branch from 26970e8 to 8ed5006 Compare November 21, 2025 10:47
@github-actions
github-actions Bot force-pushed the 1496-update-panel-memebers-to-prefered-name branch from 8ed5006 to 3ab0c33 Compare November 25, 2025 16:22
@TCMeldrum
TCMeldrum enabled auto-merge (squash) December 2, 2025 14:18
@TCMeldrum
TCMeldrum merged commit a9336e8 into develop Dec 2, 2025
36 of 37 checks passed
@TCMeldrum
TCMeldrum deleted the 1496-update-panel-memebers-to-prefered-name branch December 2, 2025 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

In FAP panels use prefered name for STFC

4 participants